Related: #328

I start thinking that for WASM support, we must change at least JS and Rust bindings to use the intermediate C layer, introducing ABI stability, and then simply shipping precompiled shared libraries for WASM. What do you think, @sroussey?

Can't ship anything that uses exceptions at the moment, at least with wasi. Quickly changing area, but still not there yet.

I am not sure about JavaScript WASM support yet, but CloudFlare recently posted an article about their Pyodide workers:

LLVM provides three target triples for WebAssembly:

• wasm32-unknown-unknown – this backend provides no C standard library or system call interface; to support this backend, we would need to manually rewrite every system or library call to make use of imports we would define ourselves in the runtime.
• wasm32-wasi – WASI is a standardized system interface, and defines a standard set of imports that are implemented in WASI runtimes such as wasmtime.
• wasm32-unknown-emscripten – Like WASI, Emscripten defines the imports that a WebAssembly program needs to execute, but also outputs an accompanying JavaScript library that implements these imported functions.

Pyodide uses Emscripten, and provides three things:

• A distribution of the CPython interpreter, compiled using Emscripten
• A foreign function interface (FFI) between Python and JavaScript
• A set of third-party Python packages, compiled using Emscripten’s compiler to WebAssembly.

I am thinking to update the setup.py to support Emscripten and other compilers, and later upload the wheel to release notes.

How to use this libraries wasm bundle.Because when I try to install with wasmer or run it gives errors.